Processing extension type system information blocks (SIBs)

ABSTRACT

A method for determining an extension type of a system information block segment is described. A system information block segment of type extension is received in a system frame number. A byte in a system information block extension type lookup table corresponding to the system frame number of the system information block segment is calculated. A bit position in the system information block extension type lookup table corresponding to the system frame number is calculated. The extension type expected at the system frame number for the system information block segment is determined using the byte and the bit position.

RELATED APPLICATIONS

This application is related to and claims priority from U.S. ProvisionalPatent Application Ser. No. 61/359,418, filed Jun. 29, 2010, for“RECEIVING AND PROCESSING OR EXTENSION SYSTEM INFORMATION BLOCKS INHSPA+ USER EQUIPMENT.”

TECHNICAL FIELD

The present disclosure relates generally to wireless communicationsystems. More specifically, the present disclosure relates to systemsand methods for processing extension type system information blocks(SIBs).

BACKGROUND

Wireless communication systems are widely deployed to provide varioustypes of communication content such as voice, video, data, and so on.These systems may be multiple-access systems capable of supportingsimultaneous communication of multiple terminals with one or more basestations.

A terminal may be battery operated. As such, it may be desirable tominimize the battery consumption of the terminal. One such way to reducethe battery consumption is to reduce computations performed by theterminal that are ambiguous. By reducing these computations, theterminal may spend less time in processing data and more time in lowpower consumption modes. Furthermore, reducing the complexity of thecomputations performed on the terminal may reduce the cost of producinga terminal.

When a terminal camps on a cell, the terminal may receive systeminformation blocks (SIBs) that instruct the terminal. Benefits may berealized by improved methods for receiving and decoding these systeminformation blocks (SIBs).

SUMMARY

A method for determining an extension type of a system information blocksegment is described. A system information block segment of typeextension is received in a system frame number. A byte in a systeminformation block extension type lookup table corresponding to thesystem frame number of the system information block segment iscalculated. A bit position in the system information block extensiontype lookup table corresponding to the system frame number is alsocalculated. The extension type expected at the system frame number forthe system information block segment is determined using the byte andthe bit position.

Bit content may correspond to the byte and the bit position. Determiningthe extension type expected using the byte and the bit position mayinclude determining the extension type corresponding to the bit contentin a bit content to system information block extension type mapping. Thesystem information block extension type lookup table may be initializedto all zeroes. Scheduling information may be received. Bits in thesystem information block extension type lookup table may be filled infor each system frame number of the scheduling information. Thescheduling information may be one of a master information block and ascheduling block.

The system information block extension type lookup table may be areduced memory system information block extension type lookup table.Only bits in the reduced memory system information block extension typelookup table for system frame numbers in the range 0 to maxRepInterval−1may be filled. The method may be performed by a user equipment. The userequipment (UE) may operate in an Evolved High-Speed Packet Accessenvironment. The system information block segment may be a broadcastcontrol channel-broadcast channel system information block segment.

The method may reduce the time used to process the system informationblock of type extension. The method may also reduce the millioninstructions per second used to process the system information block oftype extension. It may be determined whether a sfn_prime of the systeminformation block segment is equal to a scheduled system frame number.The sfn_prime of the system information block segment may be equal tothe scheduled system frame number. The system information block segmentmay then be processed. If the sfn_prime of the system information blocksegment is not equal to the scheduled system frame number, the systeminformation block segment may be discarded and a new system informationblock segment may be waited for.

A wireless device configured for determining an extension type of asystem information block segment is also described. The wireless deviceincludes a processor, memory in electronic communication with theprocessor and instructions stored in the memory. The instructions areexecutable by the processor to receive a system information blocksegment of type extension in a system frame number. The instructions arealso executable by the processor to calculate a byte in a systeminformation block extension type lookup table corresponding to thesystem frame number of the system information block segment. Theinstructions are further executable to calculate a bit position in thesystem information block extension type lookup table corresponding tothe system frame number. The instructions are also executable todetermine the extension type expected at the system frame number for thesystem information block segment using the byte and the bit position.

A wireless device configured for determining an extension type of asystem information block segment is described. The wireless deviceincludes means for receiving a system information block segment of typeextension in a system frame number. The wireless device also includesmeans for calculating a byte in a system information block extensiontype lookup table corresponding to the system frame number of the systeminformation block segment. The wireless device further includes meansfor calculating a bit position in the system information block extensiontype lookup table corresponding to the system frame number. The wirelessdevice also includes means for determining the extension type expectedat the system frame number for the system information block segmentusing the byte and the bit position.

A computer-program product for determining an extension type of a systeminformation block segment is also described. The computer-programproduct is a non-transitory computer-readable medium having instructionsthereon. The instructions include code for causing a user equipment toreceive a system information block segment of type extension in a systemframe number. The instructions also include code for causing the userequipment to calculate a byte in a system information block extensiontype lookup table corresponding to the system frame number of the systeminformation block segment. The instructions further include code forcausing the user equipment to calculate a bit position in the systeminformation block extension type lookup table corresponding to thesystem frame number. The instructions also include code for causing theuser equipment to determine the extension type expected at the systemframe number for the system information block segment using the byte andthe bit position.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a wireless communication system with multiple wirelessdevices;

FIG. 2 is a block diagram illustrating system information flows betweena user equipment (UE), a radio network controller (RNC), a circuitswitched (CS) core network and a packet switched (PS) core network;

FIG. 3 is a block diagram illustrating a scheduling tree for systeminformation blocks (SIBs);

FIG. 4 is a block diagram illustrating transmissions from a Node B to auser equipment (UE);

FIG. 5 is a block diagram illustrating the structure of a systeminformation message;

FIG. 6 is a block diagram illustrating the use of a scheduling systeminformation block (SIB) extension type table and a bit content to systeminformation block (SIB) extension type mapping to determine theextension type of a system information block (SIB) segment;

FIG. 7 is a block diagram illustrating extension type system informationblock (SIB) scheduling;

FIG. 8 is a flow diagram of a method for determining an extension typeof a system information block (SIB) segment;

FIG. 9 is a flow diagram of another method for determining an extensiontype of a system information block (SIB) segment; and

FIG. 10 illustrates certain components that may be included within awireless communication device.

DETAILED DESCRIPTION

The 3^(rd) Generation Partnership Project (3GPP) is a collaborationbetween groups of telecommunications associations that aims to define aglobally applicable 3^(rd) generation (3G) mobile phone specification.The 3GPP may define specifications for the next generation of mobilenetworks, mobile systems and mobile devices. In 3GPP, a mobile stationor device may be referred to as a “user equipment” (UE).

FIG. 1 shows a wireless communication system 100 with multiple wirelessdevices. Wireless communication systems 100 are widely deployed toprovide various types of communication content such as voice, data, andso on. A wireless device may be a Node B 104 a-d or a user equipment(UE) 116. A Node B 104 is a station that communicates with one or moreuser equipments (UEs) 116. A Node B 104 may also be referred to as, andmay include some or all of the functionality of, an access point, abroadcast transmitter, a base station, an evolved Node B, etc.

A user equipment (UE) 116 may also be referred to as, and may includesome or all of the functionality of, a terminal, an access terminal, awireless communication device, a subscriber unit, a station, etc. A userequipment (UE) 116 may be a cellular phone, a personal digital assistant(PDA), a wireless device, a wireless modem, a handheld device, a laptopcomputer, etc.

Communications in a wireless system (e.g., a multiple-access system) maybe achieved through transmissions over a wireless link. Such acommunication link may be established via a single-input andsingle-output (SISO), multiple-input and single-output (MISO) or amultiple-input and multiple-output (MIMO) system. A multiple-input andmultiple-output (MIMO) system includes transmitter(s) and receiver(s)equipped, respectively, with multiple (NT) transmit antennas andmultiple (NR) receive antennas for data transmission. SISO and MISOsystems are particular instances of a multiple-input and multiple-output(MIMO) system. The multiple-input and multiple-output (MIMO) system canprovide improved performance (e.g., higher throughput, greater capacityor improved reliability) if the additional dimensionalities created bythe multiple transmit and receive antennas are utilized.

The wireless communication system 100 may be a multiple-access systemcapable of supporting communication with multiple user equipments (UEs)116 by sharing the available system resources (e.g., bandwidth andtransmit power). Examples of such multiple-access systems include codedivision multiple access (CDMA) systems, wideband code division multipleaccess (W-CDMA) systems, time division multiple access (TDMA) systems,frequency division multiple access (FDMA) systems, orthogonal frequencydivision multiple access (OFDMA) systems, single-carrier frequencydivision multiple access (SC-FDMA) systems, 3^(rd) GenerationPartnership Project (3GPP) Long Term Evolution (LTE) systems and spatialdivision multiple access (SDMA) systems.

The wireless communication system 100 may include a radio access network(RAN) 118 operating according to Universal Mobile TelecommunicationsSystem (UMTS). A radio access network (RAN) 118 may include one or moreradio network subsystems (RNS) 108 a-b. Each radio network subsystem(RNS) 108 may include one or more Node Bs 104 and one or more radionetwork controllers (RNCs) 106 a-b. A radio access network (RAN) 118 mayalso be referred to as a “radio network” or an “access network.” Theradio access network (RAN) 118 may be a UMTS Terrestrial Radio AccessNetwork (UTRAN). A UMTS Terrestrial Radio Access Network (UTRAN) is acollective term for the Node Bs 104 and the control equipment for theNode Bs 104 (or radio network controllers (RNCs) 106 a-b) it containswhich make up the UMTS radio access network (RAN) 118. This is a thirdgeneration (3G) communications network which can carry both real-timecircuit switched and internet protocol (IP) based packet switchedtraffic types. The UTRAN provides an air interface access method for theuser equipment (UE) 116. Connectivity is provided between the userequipment (UE) 116 and a core network 102 by the UTRAN. The radio accessnetwork (RAN) 118 may transport data packets between multiple userequipments (UEs) 116.

The UTRAN may be connected internally or externally using fourinterfaces: the Iu interface 110 a-b, the Uu interface 101, the Iubinterface 114 a-d and the Iur interface 112. The UTRAN may be attachedto a Global System for Mobile Communications (GSM) core network 102 viaan external interface referred to as the Iu interface 110. One or moreradio network controllers (RNCs) 106 may support the Iu interface 110.In addition, a radio network controller (RNC) 106 may manage a set ofbase stations called Node Bs 104 through the Iub interfaces 114. The Iurinterface 112 may connect two radio network controllers (RNCs) 106 witheach other. The UTRAN is largely autonomous from the core network 102since the radio network controllers (RNCs) 106 are interconnected by theIur interface 112. The Uu interface 101 also connects the Node B 104with a user equipment (UE) 116, while the Iub interface 114 is aninternal interface that connects the radio network controller (RNC) 106with the Node B 104.

The radio access network (RAN) 118 may be further connected toadditional networks outside the radio access network (RAN) 118, such asa corporate intranet, the Internet or a conventional public switchedtelephone network (PSTN) and may transport data packets between eachuser equipment (UE) 116 and the outside networks.

The wireless communication system 100 may utilize Evolved High-SpeedPacket Access (HSPA+). Evolved High-Speed Packet Access (HSPA+) is awireless broadband standard defined in 3GPP Release 7 and above. EvolvedHigh-Speed Packet Access (HSPA+) uses multiple-input and multiple-output(MIMO) along with higher order modulation (e.g., 16 quadrature amplitudemodulation (QAM)) to increase capacity.

A user equipment (UE) 116 may include a system information block (SIB)scheduling module 120. The user equipment (UE) 116 may receive systeminformation block (SIB) segments 128 from a Node B 104. Each systeminformation block (SIB) segment 128 may include a type 130. Most types130 of system information block (SIB) segments 128 use a one-to-onemapping. However, when the type 130 of a system information block (SIB)segment 128 is Extension, the system information block (SIB) segment 128may include a one-to-many mapping to different extension types 132.There are currently 11 possible extension types 132, although more maybe used. A system information block (SIB) segment 128 of type 130extension may map to one of the extension types 132. The current 3GPPstandard specification does not specify how the user equipment (UE) 116should process system information block (SIB) segments 128 that are anextension type 132.

The user equipment (UE) 116 may use the system information block (SIB)scheduling module 120 to determine the extension type 132 of a systeminformation block (SIB) segment 128. The system information block (SIB)scheduling module 120 may use a system information block (SIB)scheduling algorithm 122 to sort through the received system informationblock (SIB) segments 128. Because of the many different extension types132, the system information block (SIB) scheduling algorithm 122 mayneed to be iteratively run. However, this can reduce the efficiency of auser equipment (UE) 116 (i.e., cause a longer running time). Instead,the user equipment (UE) 116 may include a system information block (SIB)extension type lookup table 124 that allows for a reduced running timeof the system information block (SIB) scheduling algorithm 122. Thesystem information block (SIB) scheduling module 120 may use the systeminformation block (SIB) extension type lookup table 124 and a bitcontent to system information block (SIB) extension type mapping 126 todetermine the extension type 132 of a system information block (SIB)segment 128 of type 130 extension. In one configuration, the systeminformation block (SIB) scheduling module 120 may include amaxRepInterval 137. The maxRepInterval 137 may be the maximum repetitioninterval of the system information blocks (SIBs) that are extension type132. Both the system information block (SIB) extension type lookup table124 and the bit content to system information block (SIB) extension typemapping 126 are discussed in additional detail below in relation to FIG.6. The maxRepInterval 137 is discussed in additional detail below inrelation to FIG. 8 and FIG. 9.

FIG. 2 is a block diagram illustrating system information flows betweena user equipment (UE) 216, a radio network controller (RNC) 206, acircuit switched (CS) core network 202 a and a packet switched (PS) corenetwork 202 b. The user equipment (UE) 216 of FIG. 2 may be oneconfiguration of the user equipment (UE) 116 of FIG. 1. The UMTSsignaling protocol stack may be divided into an Access Stratum (AS) anda Non-Access Stratum (NAS). The Non-Access Stratum (NAS) architecturemay include connection management. The connection management may handlecircuit switched calls. The connection management may include sub layersresponsible for call control (e.g., establish, release), supplementaryservices (e.g., call forwarding, three-way calling) and the shortmessage service (SMS).

The Non-Access Stratum (NAS) architecture may also include sessionmanagement that handles packet switched calls (e.g., establish,release). The Non-Access Stratum (NAS) architecture may further includemobility management that handles location updating and authenticationfor circuit switched calls. The Non-Access Stratum (NAS) architecturemay also include GPRS mobility management that handles location updatingand authentication for packet switched calls.

The Access Stratum (NAS) architecture may include the radio resourcecontrol (RRC) protocols, radio link control (RLC) protocols, mediaaccess control (MAC) protocols and Physical (PHY) layer protocols. Theradio resource control (RRC) protocols are defined between a userequipment (UE) 216 and the radio network controller (RNC) 206 to handlethe establishment, release and configuration of radio resources. Theradio link control (RLC) protocols are defined between the userequipment (UE) 216 and the radio network controller (RNC) 206 to providesegmentation, re-assembly, duplicate detection and other traditionalLayer 2 functions. The media access control (MAC) protocols are definedbetween a user equipment (UE) 216 and the radio network controller (RNC)206 to multiple user plane and control plane data. The Physical (PHY)layer protocols are defined between a user equipment (UE) 216 and a NodeB 104 to transfer data over the radio link. The interface between theuser equipment (UE) 216 and the radio network controller (RNC) 206 atthe Physical (PHY) layer handles macro diversity combining and splittingfunctions.

For a user equipment (UE) 216 to access a wireless network, a processcalled a cell selection procedure is performed. The cell selectionprocedure is responsible for finding a preferred or best cell to campon. The cell to be camped on may be determined by Non-Access Stratum(NAS) parameters such as a requested public land mobile network (PLMN)or a forbidden registration area list. The cell to be camped on may alsobe determined by system information received for the cell that includesthe cell barred status, public land mobile network (PLMN), Location AreaIdentity (LAI) and cell access restrictions.

A radio resource control (RRC) cell selection procedure may beresponsible for searching for a cell to camp on when entering radioresource control (RRC) Idle-Disconnected state from a connected state.The radio resource control (RRC) layer in the UTRAN may be responsiblefor broadcasting system information to all user equipments (UEs) 216.This system information may be broadcast in system information block(SIB) messages that include both Access Stratum (NAS) and Non-AccessStratum (NAS) information elements. The packet switched (PS) corenetwork 202 b may send packet switched (PS) core network broadcastinformation 234 to the radio network controller (RNC) 206. The circuitswitched (CS) core network 202 a may send circuit switched (CS) corenetwork broadcast information 236 to the radio network controller (RNC)206. The radio network controller (RNC) 206 may then send systeminformation messages 238 a-b to the user equipment (UE) 216.

When a user equipment (UE) 216 first camps on a particular cell, theuser equipment (UE) 216 reads system information messages 238 for thatcell from the broadcast channel (BCH). The user equipment (UE) 216 maystore the system information messages 238 from a given cell so that ifthe user equipment (UE) 216 changes to another cell and then laterreturns to the cell, the user equipment (UE) 216 can use the storedsystem information messages 238 rather than reading them from thebroadcast channel (BCH).

FIG. 3 is a block diagram illustrating a scheduling tree for systeminformation blocks (SIBs) 342 a-i. System information is organized intoblocks called system information blocks (SIBs) 342. A system informationblock (SIB) 342 groups together system information elements of the samenature. Different system information blocks (SIBs) 342 may havedifferent characteristics, such as repetition rate and the instructionsfor the user equipment (UE) 116 to reread the system information blocks(SIBs) 342.

There may be only one Master Information Block (MIB) 340 that includesscheduling information for the system information blocks (SIBs) 342. TheMaster Information Block (MIB) 340 may include scheduling information inone or two scheduling blocks (SBs) 344 (i.e., SB1 344 a and SB2 344 b).The one or two scheduling blocks (SBs) 344 may give schedulinginformation for additional system information blocks (SIBs) 342.

In the scheduling tree for system information blocks (SIBs) 342 shown,the Master Information Block (MIB) 340 provides scheduling for systeminformation block (SIB) type m 342 a, system information block (SIB)type n 342 b and other system information block (SIB) 342 types throughsystem information block (SIB) type p 342 c. The Master InformationBlock (MIB) 340 provides scheduling information in a first schedulingblock (SB) SB1 344 a and a second scheduling block (SB) SB2 344 b. Thefirst scheduling block (SB) SB1 344 a may then provide schedulinginformation for system information block (SIB) type q 342 d, systeminformation block (SIB) type r 342 e and other system information block(SIB) 342 types through system information block (SIB) type u 342 f. Thesecond scheduling block (SB) SB2 344 b may provide schedulinginformation for system information block (SIB) type x 342 g, systeminformation block (SIB) type y 342 h and other system information block(SIB) 342 types through system information block (SIB) type z 342 i. Auser equipment (UE) 116 may use the scheduling tree for systeminformation blocks (SIBs) 342 to determine the extension type 132 of asystem information block (SIB) segment 128. For example, a MasterInformation Block (MIB) 340 or scheduling block (SB) 344 (SB1 344 a orSB2 344 b) may indicate to the user equipment (UE) 116 the extensiontype 132 of a system information block (SIB) segment 128.

FIG. 4 is a block diagram illustrating transmissions from a Node B 404to a user equipment (UE) 416. The Node B 404 of FIG. 4 may be oneconfiguration of the Node Bs 104 of FIG. 1. The user equipment (UE) 416of FIG. 4 may be one configuration of the user equipment (UE) 116 ofFIG. 1. The Node B 404 may communicate with the physical (PHY) layer 448of the user equipment (UE) 416 using the primary common control physicalchannel (PCCPCH) 446. The Master Information Block (MIB) 340, schedulingblocks (SBs) 344 and all of the system information blocks (SIBs) 342 aretransmitted in a set of system information messages that are sent on theprimary common control physical channel (PCCPCH) 446. Then, the systeminformation blocks (SIBs) 342 can be sent to the radio resource control(RRC) layer 462 through the pipe shown from the physical (PHY) layer 448to the media access control (MAC) layer 452 via the broadcast channel(BCH) 450, from the media access control (MAC) layer 452 to the radiolink control (RLC) layer 458 via the broadcast control channel (BCCH)454 and from the radio link control (RLC) layer 458 to the radioresource control (RRC) layer 462 via a transparent mode (TM) 456 and thebroadcast control channel (BCCH) 460.

FIG. 5 is a block diagram illustrating the structure of a systeminformation message 568. Every 20 milliseconds (ms), a systeminformation message 568 is broadcast on the primary common controlphysical channel (PCCPCH) 446 with a BCCH-BCH container using primarycommon control physical channel (PCCPCH) frames 566. As used herein, aBCCH-BCH container is a container that can carry system informationblocks. The system information message 568 encapsulates and segments theMaster Information Block (MIB) 340, scheduling blocks (SBs) 344 and thesystem information block (SIB) segments 570. The system informationmessage 568 may include the System Frame Number (SFN) 564. Thetransmitted System Frame Number (SFN) 564 is even because the systeminformation message 568 is transmitted every 20 ms while the SystemFrame Number (SFN) 564 increments every 10 ms.

The system information message 568 may include one of eleven possiblesegment types: 1. No segment, 2. First segment, 3. Subsequent segment,4. Last segment, 5. Last segment plus first segment, 6. Last segmentplus complete segment list, 7. Last segment plus complete segment listplus first segment, 8. Complete segment list, 9. Complete segment listplus first segment, 10. Complete segment of size 215 to 226 or 11. Lastsegment of size 215 to 222. There may be gaps between the systeminformation blocks (SIBs) 342. The system information blocks (SIBs) 342may not necessarily follow each other in consecutive primary commoncontrol physical channel (PCCPCH) frames 566.

Scheduling of system information blocks (SIBs) 342 may be performed bythe radio resource control (RRC) layer 462 in UTRAN. If segmentation isused, it may be possible to schedule each system information block (SIB)segment 128 separately. Scheduling is a way for a user equipment (UE)116 to identify which system information block (SIB) 342 is coming onwhich System Frame Number (SFN) 564. To allow the mixing of systeminformation blocks (SIBs) 342 with a short repetition period and systeminformation blocks (SIBs) 342 with segmentation over many frames, theUTRAN may multiplex segments from different system information blocks(SIBs) 342. Multiplexing and de-multiplexing may be performed by theradio resource control (RRC) layer 462.

The scheduling of each system information block (SIB) 342 broadcast on abroadcast channel (BCH) transport channel may be defined by the numberof segments (SEG_COUNT), the repetition period (SIB_REP) (the same valueapplies to all segments), the position (phase) of the first segmentwithin one cycle of the Cell System Frame Number 564 (SIB_POS(0)) andthe offset of the subsequent segments in ascending index order(SIB_OFF(i), i=1, 2, . . . SEG_COUNT−1). Since system information blocks(SIBs) 342 are repeated with a period of SIB_REP, the value ofSIB_POS(i), i=0, 1, 2, . . . SEG_COUNT−1 is be less than SIB_REP for allsegments. The position of the subsequent segments may be calculated asSIB_POS(i)=SIB_POS(i−1)+SIB_OFF(i).

The scheduling is based on the Cell System Frame Number (SFN) 564. TheSystem Frame Number (SFN) 564 of a frame at which a particular segment i(with i=0, 1, 2, . . . SEG_COUNT−1) of a system information block (SIB)342 occurs fulfills Equation (1):SFN mod SIB_REP=SIB_POS(i).  (1)

If a system information block (SIB) segment 128 fails to pass therelationship in Equation (1), the user equipment (UE) 116 may discardthis system information block (SIB) segment 128.

The BCCH-BCH container may include the System Frame Number (SFN) prime,the type 130, the segment type and the data using one of thecombinations from 1 to 11. As used herein, System Frame Number (SFN)prime refers to the System Frame Number (SFN) multiplied by 2. Thesystem information block (SIB) type 130 is only capable of indicating atype from 1 to 31. For legacy system information blocks (SIBs) 342, auser equipment (UE) 116 can get scheduling information based on thesystem information block (SIB) type 130 directly (i.e., a one-to-onemapping). For example, if a BCCH-BCH container has system informationblock (SIB) type 130 as Master Information Block (MIB) 340, then thesystem information block (SIB) 342 maps directly to the MasterInformation Block (MIB) 340.

However, over time additional system information block (SIB) types 130have become necessary. These additional system information block (SIB)types 130 are referred to as extension types 132. An extension type 132has a system information block (SIB) type 130 of 31 (i.e., extension).Extension type 132 scheduling is discussed in additional detail below inrelation to FIG. 6.

FIG. 6 is a block diagram illustrating the use of a scheduling systeminformation block (SIB) extension type table 624 and a bit content tosystem information block (SIB) extension type mapping 626 to determinethe extension type 632 a-b of a system information block (SIB) segment628. A user equipment (UE) 116 may receive a system information block(SIB) segment 628. The system information block (SIB) segment 628 may bereceived during a System Frame Number (SFN) 664 a. The systeminformation block (SIB) segment 628 may include a type 630 that is setto extension 670. The system information block (SIB) segment 628 mayalso include an extension type 632 a. The system information block (SIB)segment 628 may further include system information block (SIB) bits 672.

To determine the extension type 632 a of a system information block(SIB) segment 628, the user equipment (UE) 116 may use a systeminformation block (SIB) extension type lookup table 624. The userequipment (UE) 116 may plug the System Frame Number (SFN) 664 b of thesystem information block (SIB) segment 628 into the system informationblock (SIB) extension type lookup table 624 and find the bit content 674a for the bit position corresponding to the System Frame Number (SFN)664 c. The user equipment (UE) 116 may use the bit content 674 b in abit content to system information block (SIB) extension type mapping626. The user equipment (UE) 116 may find the extension type 632 bcorresponding to the bit content 674 c in the bit content to systeminformation block (SIB) extension type mapping 626. The extension type632 b in the bit content to system information block (SIB) extensiontype mapping 626 may be the extension type 632 a of the systeminformation block (SIB) segment 628.

FIG. 7 is a block diagram illustrating extension type 132 systeminformation block (SIB) 342 scheduling. In extension type 132 systeminformation block (SIB) 342 scheduling, the system information block(SIB) type 130 is extension 670 (i.e., SIB type 31) that allows aone-to-many mapping of the type 130 to different extension types 132.There are 11 extension types 132: 1. systemInfoType11bis, 2.systemInfoType15bis, 3. systemInfoType15-1bis, 4. systemInfoType15-2bis,5. systemInfoType15-3bis, 6. systemInfoType15-6, 7. systemInfoType15-7,8. systemInfoType15-8, 9. systemInfoType19, 10. systemInfoType15-2terand 11. systemInfoType20. A system information block (SIB) segment 128with a type 130 that is extension 670 may map to any of the 11 extensiontypes 132.

The extension type 132 for a system information block (SIB) segment 128may be indicated only in the scheduling information in the MasterInformation Block (MIB) 340 or scheduling block (SB) 344. Each segmentin SYSTEM INFORMATION for SIB11bis only indicates the system informationblock (SIB) type 130 extension type 132 but does not providespecifically which system information block (SIB) type 130. Typically,the user equipment (UE) 116 relies on the position (in terms of thebroadcast channel (BCH) transmission time interval (TTI)) of thesegments in identifying particular segments with extension type 132corresponding to SIB 11bis.

A system information block (SIB) reception architecture of the userequipment (UE) 116 carries out a targeted reception of systeminformation blocks (SIBs) 342 based on the information provided in thescheduling information. The user equipment (UE) 116 may use a systeminformation block (SIB) scheduling module 120 with a system informationblock (SIB) scheduling algorithm 122 on every BCCH-BCH systeminformation block (SIB) segment 128 of type 130 extension 670. There arecurrently 11 different extension types 132 (although in the future,there may be more). Each extension type 132 may have 16 segments.Assuming that the system information block (SIB) scheduling algorithm122 is not optimized, the system information block (SIB) schedulingalgorithm 122 can potentially run many times.

For example, the user equipment (UE) 116 may internally bookmark asystem information block (SIB) segment 128 of extension type 132 asreceived once it is received and decoded successfully. Henceforth, theuser equipment (UE) 116 does not consider this extension type 132 whilerunning the system information block (SIB) scheduling algorithm 122. Ifthe system information block (SIB) scheduling algorithm 122 is first runfor extension type 1, then run for extension type 2 and so on, for thebest case scenario (i.e., when the user equipment (UE) 116 receives asegment of extension type 1 (i.e., SIB11bis) first, followed byreceiving a segment of extension type 2 (i.e., SIB15bis) and so on), thesystem information block (SIB) scheduling algorithm may be run 11*16=176times. For the worst case scenario (i.e., when the user equipment (UE)116 receives a segment of extension type 11 (i.e., SIB20) first,followed by receiving a segment of extension type 10 (i.e., SIB15-2ter)and so on), the system information block (SIB) scheduling algorithm 122may be run (1+2+3+4+5+6+7+8+9+10+11)*16=1056 times, assuming that systeminformation block (SIB) 342 decoding does not fail.

Different MIBs/SIBs may be received for each System Frame Number (SFN).In the example shown in FIG. 7, a Master Information Block (MIB) 776 auses SFN 8 and SFN 9. The Master Information Block (MIB) 776 a isfollowed by a system information block (SIB) segment 128 of extensiontype 1 (i.e., SIB11bis 776 b) in SFN 10 and SFN 11. A system informationblock (SIB) segment 128 of extension type 9 (i.e., SIB19bis 776 c) is inSFN 12 and SFN 13. A system information block (SIB) segment 128 ofextension type 2 (i.e., SIB15bis 776 d) is in SFN 14 and SFN 15. AMaster Information Block (MIB) 776 e uses SFN 16 and SFN 17. A systeminformation block (SIB) segment 128 of extension type 11 (i.e., SIB20776 f) uses SFN 18 and SFN 19. A system information block (SIB) segment128 of extension type 10 (i.e., SIB15-2ter 776 g) uses SFN 20, SFN 21,SFN 22 and SFN 23. A Master Information Block (MIB) 776 h uses SFN 24and SFN 25.

FIG. 8 is a flow diagram of a method 800 for determining an extensiontype 132 of a system information block (SIB) segment 128. The method 800may be performed by a user equipment (UE) 116. The user equipment (UE)116 may receive 802 a BCCH-BCH system information block (SIB) segment128 of type 130 extension 670. A system information block (SIB) segment128 of type 130 extension 670 is a system information block (SIB)segment 128 with type 130 extension 670 (i.e., SIB type 31) indicatingthat one of the extension types 132 is used for the system informationblock (SIB) segment 128.

The user equipment (UE) 116 may calculate 804 the byte in a systeminformation block (SIB) extension type lookup table 124 corresponding tothe System Frame Number (SFN) 564 prime of the received BCCH-BCH systeminformation block (SIB) segment 128. The system information block (SIB)extension type lookup table 124 may be a table with 1024 bytesmaintained by the user equipment (UE) 116. Every four bits of each bytemay correspond to a System Frame Number (SFN) 564 prime. For example,bits 0, 1, 2 and 3 of the first byte (byte 1) may map to SFN prime 0 andbits 4, 5, 6 and 7 of the first byte (byte 1) may map to SFN prime 1.The system information block (SIB) extension type lookup table 124limits the extension types 132 that are used in the system informationblock (SIB) scheduling algorithm 122. The initialization of the systeminformation block (SIB) extension type lookup table 124 is discussedbelow in relation to FIG. 9. The bit positions and bytes for differentSystem Frame Number (SFN) 564 primes in a system information block (SIB)extension type lookup table 124 are illustrated in Table 1 below.

TABLE 1 Bit positions 0 1 2 3 4 5 6 7 Byte 1 SFN prime 0 SFN prime1 Byte2 SFN prime 2 SFN prime 3 . . . . . . . . . Byte 1024 SFN prime 2047 SFNprime 2048

The user equipment (UE) 116 may calculate 804 the byte in the systeminformation block (SIB) extension type lookup table 124 according to theSystem Frame Number (SFN) 564 prime of the received system informationblock (SIB) segment 128 using Equation (2):Byte index=SFN prime>>1.  (2)

In Equation (2), “>>1” means a right shift by 1. The user equipment (UE)116 may calculate 806 a bit position in the system information block(SIB) extension type lookup table 124 corresponding to the System FrameNumber (SFN) 564 prime using Equation (3):Bit position=SFN prime & 0x1.  (3)

Based on the bit content 674 found at the bit position and byte of thesystem information block (SIB) extension type lookup table 124, the userequipment (UE) 116 may determine 808 the system information block (SIB)extension type 132 using a bit content to system information block (SIB)extension type mapping 126. The bit content to system information block(SIB) extension type mapping 126 is illustrated in Table 2 below.

TABLE 2 Bit Extension content type 0001 SIB11bis 0010 SIB15bis 0011SIB15-1bis 0100 SIB15-2bis 0101 SIB15-3bis 0110 SIB15-6 0111 SIB15-71000 SIB15-8 1001 SIB19 1010 SIB15-2ter 1011 SIB20

One benefit of determining the extension type 132 using the method 800is that the system information block (SIB) scheduling algorithm 122 doesnot need to be computed iteratively. Also, the operations involved toderive the extension type 132 are simple bitwise operations with noconditional branching. The million instructions per second (MIPS)consumed for receiving and decoding the system information block (SIB)segments 128 of type 130 extension 670 may be lower (i.e., reduced)using the method 800 than using the system information block (SIB)scheduling algorithm 122 iteratively.

In one configuration, a reduced memory system information block (SIB)extension type lookup table 124 may be used to determine extension types132. The size of the reduced memory system information block (SIB)extension type lookup table 124 may be limited based upon repeatintervals of the extension types 132. In the reduced memory systeminformation block (SIB) extension type lookup table 124, only the SystemFrame Number (SFN) 564 primes in the range 0 to maxRepInterval−1 may befilled. The interval maxRepInterval 137 is the maximum repetitioninterval of the system information blocks (SIBs) 342 that are extensiontype 132, in terms of the number of System Frame Numbers (SFNs) 564. Thesize of the reduced memory system information block (SIB) extension typelookup table 124 may be maxRepInterval*4/8 bytes.

Calculating a byte in the reduced memory system information block (SIB)extension type lookup table 124 corresponding to the System Frame Number(SFN) 564 prime of the received BCCH-BCH system information block (SIB)segment 128 may use Equation (4):Byte index=(SFN prime & (maxRepInterval−1)2)>>1.  (4)

In Equation (4), (maxRepInterval−1) is multiplied by 2. Also, inEquation (4), “>>1” refers to a shift to the right by 1. In practicalnetworks, the value of maxRepInterval 137 may be 128. Equation (4) maythen be rewritten as Equation (5):Byte index=(SFN prime & (0x7F)>>1.  (5)

Calculating a bit position in the reduced memory system informationblock (SIB) extension type lookup table 124 corresponding to the SystemFrame Number (SFN) 564 prime may use Equation (3) above. By checking theentry at the bit position computed using Equation (5) and Equation (3),the user equipment (UE) 116 may determine the extension type 132expected at the System Frame Number (SFN) 564 for the BCCH-BCH systeminformation block (SIB) segment. The number of MIPS consumed when usinga reduced memory system information block (SIB) extension type lookuptable 124 may be less than using the system information block (SIB)scheduling algorithm 122 iteratively. If maxRepInterval 137 is 128, thetable size in the reduced memory system information block (SIB)extension type lookup table 124 may be only 64 bytes.

FIG. 9 is a flow diagram of another method 900 for determining anextension type 132 of a system information block (SIB) segment 128. Themethod 900 may be performed by a user equipment (UE) 116. The userequipment (UE) 116 may initialize 902 a system information block (SIB)extension type lookup table 124 to all zeroes. In one configuration, thesystem information block (SIB) extension type lookup table 124 may be areduced memory system information block (SIB) extension type lookuptable 124. The user equipment (UE) 116 may receive 904 an MIB/SB1/SB2.The user equipment (UE) 116 may then fill in 906 the bits in the systeminformation block (SIB) extension type lookup table 124 for each SystemFrame Number (SFN) 564 prime according to Table 1 above. For example,for SIB11bis, the bit content 0001 may be filled in the System FrameNumber (SFN) 564 primes in which SIB11bis is scheduled as per theinformation indicated in MIB/SB1/SB2. If the system information block(SIB) extension type lookup table 124 is a reduced memory systeminformation block (SIB) extension type lookup table 124, the contents ofthe reduced memory system information block (SIB) extension type lookuptable 124 may only be filled for System Frame Number (SFN) primes 564 inthe range 0 to maxRepInterval−1.

The user equipment (UE) 116 may receive 908 a system information block(SIB) segment 128 of type 130 extension 670. The user equipment (UE) 116may determine 910 the extension type 132 of the system information block(SIB) segment 128 of type 130 extension 670. The user equipment (UE) 116may then determine 912 whether the system information block (SIB)segment sfn_prime is equal to the scheduled System Frame Number (SFN)564. If the system information block (SIB) 342 sfn_prime is not equal tothe scheduled System Frame Number (SFN) 564, the user equipment (UE) 116may discard 914 the system information block (SIB) segment 128 of type130 extension 670 and wait 916 for new system information block (SIB)segments 128/new events.

If the system information block (SIB) 342 sfn_prime (i.e., the SystemFrame Number (SFN) prime) is equal to the scheduled System Frame Number(SFN) 564, the user equipment (UE) 116 may process 918 the systeminformation block (SIB) segment 128 of type 130 extension 670.Processing 918 the system information block (SIB) segment 128 refers torunning the system information block (SIB) scheduling algorithmsdiscussed above in relation to FIGS. 2-5.

FIG. 10 illustrates certain components that may be included within awireless communication device 1001. A wireless communication device 1001may also be referred to as, and may include some or all of thefunctionality of, a terminal, an access terminal, a subscriber unit, astation, a user equipment (UE) 116, etc. The wireless communicationdevice 1001 includes a processor 1003. The processor 1003 may be ageneral purpose single- or multi-chip microprocessor (e.g., an ARM), aspecial purpose microprocessor (e.g., a digital signal processor (DSP)),a microcontroller, a programmable gate array, etc. The processor 1003may be referred to as a central processing unit (CPU). Although just asingle processor 1003 is shown in the wireless communication device 1001of FIG. 10, in an alternative configuration, a combination of processors(e.g., an ARM and DSP) could be used.

The wireless communication device 1001 also includes memory 1005. Thememory 1005 may be any electronic component capable of storingelectronic information. The memory 1005 may be embodied as random accessmemory (RAM), read only memory (ROM), magnetic disk storage media,optical storage media, flash memory devices in RAM, on-board memoryincluded with the processor, EPROM memory, EEPROM memory, registers, andso forth, including combinations thereof.

Data 1007 a and instructions 1009 a may be stored in the memory 1005.The instructions 1009 a may be executable by the processor 1003 toimplement the methods disclosed herein. Executing the instructions 1009a may involve the use of the data 1007 a that is stored in the memory1005. When the processor 1003 executes the instructions 1009 a, variousportions of the instructions 1009 b may be loaded onto the processor1003, and various pieces of data 1007 b may be loaded onto the processor1003.

The wireless communication device 1001 may also include a transmitter1011 and a receiver 1013 to allow transmission and reception of signalsto and from the wireless communication device 1001. The transmitter 1011and receiver 1013 may be collectively referred to as a transceiver 1015.Multiple antennas 1017 a-b may be electrically coupled to thetransceiver 1015. The wireless communication device 1001 may alsoinclude (not shown) multiple transmitters, multiple receivers, multipletransceivers and/or additional antennas.

The wireless communication device 1001 may include a digital signalprocessor (DSP) 1021. The wireless communication device 1001 may alsoinclude a communications interface 1023. The communications interface1023 may allow a user to interact with the wireless communication device1001.

The various components of the wireless communication device 1001 may becoupled together by one or more buses, which may include a power bus, acontrol signal bus, a status signal bus, a data bus, etc. Forsimplicity, the various buses are illustrated in FIG. 10 as a bus system1019.

The techniques described herein may be used for various communicationsystems, including communication systems that are based on an orthogonalmultiplexing scheme. Examples of such communication systems includeOrthogonal Frequency Division Multiple Access (OFDMA) systems,Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, andso forth. An OFDMA system utilizes orthogonal frequency divisionmultiplexing (OFDM), which is a modulation technique that partitions theoverall system bandwidth into multiple orthogonal sub-carriers. Thesesub-carriers may also be called tones, bins, etc. With OFDM, eachsub-carrier may be independently modulated with data. An SC-FDMA systemmay utilize interleaved FDMA (IFDMA) to transmit on sub-carriers thatare distributed across the system bandwidth, localized FDMA (LFDMA) totransmit on a block of adjacent sub-carriers, or enhanced FDMA (EFDMA)to transmit on multiple blocks of adjacent sub-carriers. In general,modulation symbols are sent in the frequency domain with OFDM and in thetime domain with SC-FDMA.

In the above description, reference numbers have sometimes been used inconnection with various terms. Where a term is used in connection with areference number, this may be meant to refer to a specific element thatis shown in one or more of the Figures. Where a term is used without areference number, this may be meant to refer generally to the termwithout limitation to any particular Figure.

The term “determining” encompasses a wide variety of actions and,therefore, “determining” can include calculating, computing, processing,deriving, investigating, looking up (e.g., looking up in a table, adatabase or another data structure), ascertaining and the like. Also,“determining” can include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory) and the like. Also,“determining” can include resolving, selecting, choosing, establishingand the like.

The phrase “based on” does not mean “based only on,” unless expresslyspecified otherwise. In other words, the phrase “based on” describesboth “based only on” and “based at least on.”

The functions described herein may be stored as one or more instructionson a processor-readable or computer-readable medium. The term“computer-readable medium” refers to any available medium that can beaccessed by a computer or processor. By way of example, and notlimitation, such a medium may comprise RAM, ROM, EEPROM, flash memory,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to storedesired program code in the form of instructions or data structures andthat can be accessed by a computer or processor. Disk and disc, as usedherein, includes compact disc (CD), laser disc, optical disc, digitalversatile disc (DVD), floppy disk and Blu-ray® disc where disks usuallyreproduce data magnetically, while discs reproduce data optically withlasers. It should be noted that a computer-readable medium may betangible and non-transitory. The term “computer-program product” refersto a computing device or processor in combination with code orinstructions (e.g., a “program”) that may be executed, processed orcomputed by the computing device or processor. As used herein, the term“code” may refer to software, instructions, code or data that is/areexecutable by a computing device or processor.

Software or instructions may also be transmitted over a transmissionmedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL) or wireless technologiessuch as infrared, radio and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL or wireless technologies such asinfrared, radio and microwave are included in the definition oftransmission medium.

Further, it should be appreciated that modules and/or other appropriatemeans for performing the methods and techniques described herein, suchas those illustrated by FIG. 8 and FIG. 9, can be downloaded and/orotherwise obtained by a device. For example, a device may be coupled toa server to facilitate the transfer of means for performing the methodsdescribed herein. Alternatively, various methods described herein can beprovided via a storage means (e.g., random access memory (RAM),read-only memory (ROM), a physical storage medium such as a compact disc(CD) or floppy disk, etc.), such that a device may obtain the variousmethods upon coupling or providing the storage means to the device.Moreover, any other suitable technique for providing the methods andtechniques described herein to a device can be utilized.

The methods disclosed herein comprise one or more steps or actions forachieving the described method. The method steps and/or actions may beinterchanged with one another without departing from the scope of theclaims. In other words, unless a specific order of steps or actions isrequired for proper operation of the method that is being described, theorder and/or use of specific steps and/or actions may be modifiedwithout departing from the scope of the claims.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the systems, methods, and apparatus described herein withoutdeparting from the scope of the claims.

No claim element is to be construed under the provisions of 35 U.S.C.§112, sixth paragraph, unless the element is expressly recited using thephrase “means for” or, in the case of a method claim, the element isrecited using the phrase “step for.”

What is claimed is:
 1. A method for determining an extension type of asystem information block segment, comprising: receiving, from a Node B,a system information block segment of type extension in a system framenumber at a user equipment; calculating, at the user equipment, a bytein a system information block extension type lookup table correspondingto the system frame number of the system information block segment;calculating, at the user equipment, a bit position in the systeminformation block extension type lookup table corresponding to thesystem frame number; and determining, at the user equipment, theextension type expected at the system frame number for the systeminformation block segment using the byte and the bit position.
 2. Themethod of claim 1, wherein bit content corresponds to the byte and thebit position, and wherein determining the extension type expected usingthe byte and the bit position comprises determining the extension typecorresponding to the bit content in a bit content to system informationblock extension type mapping.
 3. The method of claim 1, furthercomprising: initializing the system information block extension typelookup table to all zeroes; receiving scheduling information; andfilling in bits in the system information block extension type lookuptable for each system frame number of the scheduling information.
 4. Themethod of claim 3, wherein the scheduling information is one of a masterinformation block and a scheduling block.
 5. The method of claim 3,wherein the system information block extension type lookup table is areduced memory system information block extension type lookup table, andwherein only bits in the reduced memory system information blockextension type lookup table for system frame numbers in the range 0 tomaxRepinterval−1 are filled.
 6. The method of claim 1, wherein themethod is performed by a user equipment.
 7. The method of claim 6,wherein the user equipment (UE) operates in an Evolved High-Speed PacketAccess environment.
 8. The method of claim 1, wherein the systeminformation block segment is a broadcast control channel-broadcastchannel system information block segment.
 9. The method of claim 1,wherein the method reduces the time used to process the systeminformation block of type extension.
 10. The method of claim 1, whereinthe method reduces the million instructions per second used to processthe system information block of type extension.
 11. The method of claim1, further comprising determining whether a sfn_prime of the systeminformation block segment is equal to a scheduled system frame number.12. The method of claim 11, wherein the sfn_prime of the systeminformation block segment is equal to the scheduled system frame number,and further comprising processing the system information block segment.13. The method of claim 11, wherein the sfn_prime of the systeminformation block segment is not equal to the scheduled system framenumber, and further comprising: discarding the system information blocksegment; and waiting for a new system information block segment.
 14. Awireless device configured for determining an extension type of a systeminformation block segment, comprising: a processor; memory in electroniccommunication with the processor; instructions stored in the memory, theinstructions being executable by the processor to: receive a systeminformation block segment of type extension in a system frame number;calculate a byte in a system information block extension type lookuptable corresponding to the system frame number of the system informationblock segment; calculate a bit position in the system information blockextension type lookup table corresponding to the system frame number;and determine the extension type expected at the system frame number forthe system information block segment using the byte and the bitposition.
 15. The wireless device of claim 14, wherein bit contentcorresponds to the byte and the bit position, and wherein theinstructions executable to determine the extension type expected usingthe byte and the bit position comprise instructions executable todetermine the extension type corresponding to the bit content in a bitcontent to system information block extension type mapping.
 16. Thewireless device of claim 14, wherein the instructions are furtherexecutable to: initialize the system information block extension typelookup table to all zeroes; receive scheduling information; and fill inbits in the system information block extension type lookup table foreach system frame number of the scheduling information.
 17. The wirelessdevice of claim 16, wherein the scheduling information is one of amaster information block and a scheduling block.
 18. The wireless deviceof claim 16, wherein the system information block extension type lookuptable is a reduced memory system information block extension type lookuptable, and wherein only bits in the reduced memory system informationblock extension type lookup table for system frame numbers in the range0 to maxRepinterval−1 are filled.
 19. The wireless device of claim 14,wherein the wireless device is a user equipment.
 20. The wireless deviceof claim 19, wherein the user equipment (UE) operates in an EvolvedHigh-Speed Packet Access environment.
 21. The wireless device of claim14, wherein the system information block segment is a broadcast controlchannel-broadcast channel system information block segment.
 22. Thewireless device of claim 14, wherein the wireless device uses a reducedtime to process the system information block of type extension.
 23. Thewireless device of claim 14, wherein the method uses a reduced millioninstructions per second to process the system information block of typeextension.
 24. The wireless device of claim 14, wherein the instructionsare further executable to determine whether a sfn_prime of the systeminformation block segment is equal to a scheduled system frame number.25. The wireless device of claim 24, wherein the sfn_prime of the systeminformation block segment is equal to the scheduled system frame number,and wherein the instructions are further executable to process thesystem information block segment.
 26. The wireless device of claim 24,wherein the sfn_prime of the system information block segment is notequal to the scheduled system frame number, and wherein the instructionsare further executable to: discard the system information block segment;and wait for a new system information block segment.
 27. A wirelessdevice configured for determining an extension type of a systeminformation block segment, comprising: means for receiving a systeminformation block segment of type extension in a system frame number;means for calculating a byte in a system information block extensiontype lookup table corresponding to the system frame number of the systeminformation block segment; means for calculating a bit position in thesystem information block extension type lookup table corresponding tothe system frame number; and means for determining the extension typeexpected at the system frame number for the system information blocksegment using the byte and the bit position.
 28. The wireless device ofclaim 27, wherein bit content corresponds to the byte and the bitposition, and wherein the means for determining the extension typeexpected using the byte and the bit position comprises means fordetermining the extension type corresponding to the bit content in a bitcontent to system information block extension type mapping.
 29. Thewireless device of claim 27, further comprising: means for initializingthe system information block extension type lookup table to all zeroes;means for receiving a scheduling block; and means for filling in bits inthe system information block extension type lookup table for each systemframe number of the scheduling block.
 30. A computer-program product fordetermining an extension type of a system information block segment, thecomputer-program product comprising a non-transitory computer-readablemedium having computer-readable instructions encoded thereon, where thecomputer-readable instructions when executed by a computer cause thecomputer to: causing a user equipment to receive a system informationblock segment of type extension in a system frame number; causing theuser equipment to calculate a byte in a system information blockextension type lookup table corresponding to the system frame number ofthe system information block segment; causing the user equipment tocalculate a bit position in the system information block extension typelookup table corresponding to the system frame number; and causing theuser equipment to determine the extension type expected at the systemframe number for the system information block segment using the byte andthe bit position.
 31. The computer-program product of claim 30, whereinbit content corresponds to the byte and the bit position, and whereinthe causing the user equipment to determine the extension type expectedusing the byte and the bit position comprises causing the user equipmentto determine the extension type corresponding to the bit content in abit content to system information block extension type mapping.
 32. Thecomputer-program product of claim 30, wherein the instruction furthercomprise: causing the user equipment to initialize the systeminformation block extension type lookup table to all zeroes; causing theuser equipment to receive a scheduling block; and causing the userequipment to fill in bits in the system information block extension typelookup table for each system frame number of the scheduling block.